Usb hvac service verification

ABSTRACT

An HVAC system includes an enclosure for containing components of the HVAC system. Associated with the enclosure is an HVAC system control unit including a microcontroller for controlling an operation of the HVAC system. The HVAC system control unit further includes a memory associated with the microcontroller and configured to store data associated with operation of the HVAC system. The microcontroller is configurable to directly transfer the data between the memory and a portable flash memory device. The HVAC system control unit further includes a portable flash memory device interface for coupling the portable flash memory device directly thereto.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application Ser.No. 61/180,405, filed by Mark Beste, et al., on May 21, 2009, entitled“Comprehensive HVAC Control System,” commonly assigned with thisapplication and incorporated herein by reference.

TECHNICAL FIELD

This application is directed, in general, to a heating, ventilation andair conditioning (HVAC) and, more specifically, to control andconfiguration of HVAC systems.

BACKGROUND

HVAC systems are typically serviced on a regular or intermittent basisfor installation, repair and maintenance. An owner of an HVAC systembeing serviced typically contracts with a local HVAC service provider toperform such service. The service provider or an agent thereof performsthe contracted service by visiting the site of the HVAC system. Thesystem may be located in a location that is difficult to reach, such asa building rooftop. Such locations are not easily amenable totransporting equipment to the HVAC system site, especially heavy and/orbulky equipment. Exposure to the elements discourages use of someequipment, such as computers that have not been hardened to operate inadverse environmental conditions. Furthermore, in many cases a servicetechnician may not be trusted with possession of valuable electronicdevices such as a portable computer.

SUMMARY

One aspect provides an HVAC system including an enclosure for containingcomponents of the HVAC system. Associated with the enclosure is an HVACsystem control unit including a microcontroller for controlling anoperation of the HVAC system. The HVAC system control unit furtherincludes a memory associated with the microcontroller and configured tostore data associated with operation of the HVAC system. Themicrocontroller is configurable to directly transfer the data betweenthe memory and a portable flash memory device. The HVAC system controlunit further includes a portable flash memory device interface forcoupling the portable flash memory device directly thereto.

Another aspect provides a method of manufacturing an HVAC system. Themethod includes configuring an enclosure to contain components of anHVAC system. An HVAC system control unit is located within the enclosureand includes a microcontroller for controlling an operation of the HVACsystem. A parameter memory associated with the microcontroller isincluded within the HVAC system control unit. The method furtherincludes configuring the parameter memory to store data associated withoperation of the HVAC system. The microcontroller is configurable todirectly transfer the data between the memory and a portable flashmemory device. The HVAC system control unit is provided with a portableflash memory device interface for coupling the portable flash memorydevice directly to the microcontroller.

Yet another aspect provides an HVAC system control unit, including amicrocontroller. The microcontroller is configured to controlling anoperation of an HVAC system. A memory associated with themicrocontroller is configured to store data associated with operation ofthe HVAC system, and further configurable to directly transfer the databetween the memory and a portable flash memory device. The HVAC systemcontrol unit includes a portable flash memory device interface forcoupling the portable flash memory device directly to themicrocontroller.

BRIEF DESCRIPTION

Reference is now made to the following descriptions taken in conjunctionwith the accompanying drawings, in which:

FIG. 1 illustrates a cluster of HVAC systems on a rooftop;

FIG. 2 illustrates an HVAC system of the disclosure including an HVACsystem control unit;

FIG. 3 illustrates an HVAC system control unit including a portableflash memory device port;

FIG. 4 illustrates a schematic of an embodiment of the HVAC systemcontrol unit;

FIG. 5 presents a method of servicing an HVAC system;

FIG. 6 illustrates an HVAC system profile;

FIG. 7 presents a method of verifying service to an HVAC system; and

FIGS. 8A and 8B present a method manufacturing an HVAC system.

DETAILED DESCRIPTION

Commercial HVAC system operators, such as a corporation, partnership, anindividual, or any other entity that contracts with a HVAC serviceprovider for maintenance of an HVAC system, are increasingly concernedabout the quality of service performed on HVAC systems by HVAC serviceproviders (corporate or individual service technicians), e.g., theimpact on energy efficiency, and the desire to control service expenses.Completeness of service, future service needs, and anticipated capitalimprovements are determined from data collected from currently operatedHVAC systems. Moreover, operators seek to ensure that services performedare handled efficiently, quickly, and cost-effectively. However, thedata available to the operators is incomplete.

Some information regarding a HVAC unit is provided by a servicetechnician who visits the unit to perform installation, repairs ormaintenance. However, such information is typically limited in scope,and the operator has no way to verify if the reported data are correct.In some cases, an HVAC system is networked, with some data related tothe operation of the HVAC system being available to the operator.However, in conventional HVAC operation such data do not guarantee thatthe service technician has physically visited the HVAC unit. Thus, theoperator has no way to verify that repairs that do not modify dataobtained via the network have been performed as contracted.

In a related aspect of HVAC maintenance, call-in service centers mayprovide assistance to a service technician or HVAC system operator. Aremote service provider located at the call-in center is often placed inthe position of attempting to solve complex issues without detailed dataregarding the subject HVAC system. There thus exists a need to providethe remote service provider with precise and timely data from the HVACunit to improve efficiency and effectiveness of call-in center support.

Some HVAC systems are configured to accept a connection from a portablecomputer, e.g. a laptop computer. Such a connection may be used, e.g.,during the manufacturing process to configure the HVAC system. However,the utility of such a connection after the HVAC system is installed isextremely limited, as service technicians frequently do not have aportable computer, and the site of installation, e.g., outdoors, oftenon a building roof, is generally poorly suited for portable computers.In addition, the weight of the portable computer may create difficultyor hazard to the service technician when accessing a rooftop HVACsystem, e.g., climbing a ladder.

None of Trane, Carrier, York, Aaon or other residential or commercialHVAC manufacturers are known to have recognized the benefits provided bythe various embodiments provided herein. Thus, the need exists to verifyservice, document changes, and provide a lightweight method to transferinformation.

The present disclosure benefits from the unique recognition thatportable and inexpensive flash memory may be advantageously used in anHVAC service setting for various purposes to speed service, reduce thecost of service, and ensure service is performed. Portable flash memorydevices (PFMDs) have become ubiquitous in consumer electronics. Readilyavailable and relatively insensitive to water and dirt, these devicesprovide a convenient medium for data transfer by an HVAC servicetechnician in various embodiments described herein. The followingdescription is provided in the context of rooftop commercial HVAC units,but the disclosure is not limited thereto. For example, an HVAC system120 may be commercial or residential, located on a rooftop or at groundlevel.

Turning initially to FIG. 1, a cluster 110 of HVAC systems 120 a-120 fis located on a rooftop of a building 130. The HVAC systems 120 may beconfigured to cool the interior space of the building 130. The cluster110 may be managed via a centralized management system operated by anowner or lessee of the building 130. For example, the building 130 maybe one of many retail stores operated by a national chain. The storeowner may manage the cluster 110 from a central location to monitorenergy consumption and provide general maintenance.

FIG. 2 illustrates internal aspects of the HVAC system 120, sometimesreferred herein to simply as the system 120. The system 120 includes anenclosure 205 for containing various components of the system 120. Thesystem 120 includes a compressor 210, a condenser coil 220 and anevaporator coil 230. The operation of the system 120 is describedwithout limitation in the context of cooling air in an interior space ofthe building 130. The compressor 210 compresses a refrigerant that flowsto the condenser coil 220 over which a fan 240 moves air to transferheat to the ambient environment. The refrigerant flows through anexpansion valve 250, cools and flows through the evaporator coil 230.Air from an interior space being conditioned by the system 120 is cooledas it is moved past the evaporator coil 230 by a blower 260. Theoperation of the various components of the system 120 is controlled atleast in part by an HVAC system control unit 270, or simply control unit270. The system 120 is an integrated HVAC system, including both thecondenser coil 220 and the evaporator coil 230 within the enclosure 205.Other HVAC systems are also within the scope of the disclosure,including indoor units, outdoor units, attic units, and heat pumps.

FIG. 3 illustrates an embodiment of the control unit 270, presentedwithout limitation. The control unit 270 may include a display 310 andan input keypad 320. The display 310 may present various menus,parameters, and other configuration information to a user. The keypad320 may accept user input to make selections presented to the user bythe display 310, navigate among menus, and input configurationparameters. Selections may be finalized by an enter button 325. Thecontrol unit 270 may advantageously include a menu map 330 for referenceby the user when interacting with the control unit 270.

The control unit 270 also includes a portable flash memory device (PFMD)port 340. The port 340 may be a hard-wire port or may include a wirelessport that can communicate wirelessly with a PFMD device. In oneembodiment, the PFMD port 340 is configured to couple a PFMD to thecontrol unit 270. The PFMD port 340 is illustrated without limitation asa universal serial bus (USB) port. However, embodiments contemplated bythe disclosure more generally include any conventional orfuture-developed portable device including flash memory (FM) orequivalent. Herein and in the claims, FM includes without limitation,e.g., USB flash memory, also known as thumb drives, jump drives, pendrives, and other colloquial terms; Memory Stick™; SmartMedia™, CompactFlash™ (CF) in its various revisions and form factors; Secure Digital™(SD); and any other functional equivalent of the aforementioned flashmemory types, including future-developed portable rewritable solid statememory technology. Hereinafter the disclosure may present variousembodiments with reference to the USB FM. Such embodiments are presentedwithout limitation to the type of FM employed.

Turning to FIG. 4, an example embodiment of the system control unit 270is illustrated without limitation. The control unit 270 includes, aspreviously described, the keypad 320, the display 310 and the PFMD port340. A microcontroller 410 accepts inputs from the keypad 320 andprovides output data to the display 310. The microcontroller 410 may beany conventional or future developed microcontroller, microprocessor orstate machine, e.g. The microcontroller 410 operates in response toprogram instructions read from a conventional program memory 420 tocontrol aspects of the operation of the HVAC system 120. The programinstructions are sometimes referred to as “firmware.” The program memory420 may include both nonvolatile memory for persistent storage ofprogram instructions and volatile memory for temporary storage of data.The memory may also include rewritable memory, e.g., flash memory, toallow for updating of the program instructions.

Among the functions of the microcontroller 410 is storage in aconventional parameter memory 430 of parameters associated withoperation of the system 120. Parameters may include, e.g., hardwareconfiguration settings, component serial numbers, installed options,hardware revisions, control algorithm coefficients, operational data,diagnostics, service history, temperature set points and setback times.The parameter memory 430 may be volatile or nonvolatile, though invarious embodiments nonvolatile memory, e.g. flash memory, may bepreferred to retain stored parameters if power to the system 120 isinterrupted.

The microcontroller 410 interacts with other components of the system120 via a system interface 440. The system interface 440 may includenecessary electronic components to address various components of thesystem 120, and to provide control signals at appropriate voltagelevels. A network interface 450 may provide an interface to a network,e.g., a local area network (LAN) or the internet. The network interface450 may allow monitoring of various operational aspects of the system120, such as operational status, and power consumption. A computerinterface 460 provides a means to couple a computer to the control unit270. The computer interface 460 is conventionally used to configure thesystem 120 during the manufacturing process, e.g.

A PFM interface 470 couples the microcontroller 410 to a PFMD 480. ThePFM interface 470 provides any necessary signal buffering and/or addressencoding/decoding and/or control signals necessary to read from or writeto memory locations within the PFMD 480. In some embodiments the PFMinterface 470 is wholly contained within the functionality of themicrocontroller 410. In other embodiments the PFM interface 470 isimplemented by one or more components separate and distinct from themicrocontroller 410.

The program memory 420 includes instructions that configure themicrocontroller 410 to transfer data between the PFMD 480 and theparameter memory 430. In various embodiments such transfer is inresponse to commands entered by a user via the keypad 320. In someembodiments, the microcontroller 410 is configurable to recognize thepresence of the PFMD 480 when the PFMD 480 is inserted into the PFMDport 340, and to automatically transfer data between the parametermemory 430 and the PFMD 480 without the need for a user command.

The PFMD port 340 provides a means for the service technician todirectly transfer data between the PFMD 480 and the parameter memory430. Herein and in the claims, the phrase “directly transfer” andvariations thereof mean that data are transferred between the PFMD 480and the parameter memory 430 without the involvement of an interveningcomputer, such as a portable computer or network server. Themicrocontroller 410 is not an intervening computing device in thiscontext.

In various embodiments, the microcontroller 410 stores systemconfiguration data in the parameter memory 430 in a system profile,e.g., a binary or ASCII file. The system profile may include variousparameters associated with operation of the system 120. In someembodiments the system profile includes several hundred individualsettings. In particular, the parameters may define an operationalconfiguration of the system 120 that defines the behavior of the system120. By this it is meant two systems 120 that are similarly configuredwith respect to HVAC components (compressor, fans, blowers, etc.) willbehave essentially in the same manner in all operationally significantaspects when a particular system profile is installed on both systems.Thus, e.g., systems 120 in the cluster 110 may be configured to operatein a same manner by installation of a common configuration file on eachsystem 120 in the cluster 110.

FIG. 5 illustrates a method generally designated 500 of servicing anHVAC system that advantageously benefits from the transferability of theconfiguration file via the PFMD 480. In a step 510, a service provider,e.g., HVAC technician, transfers a configuration profile from a firstHVAC system 120 to the PFMD 480. The HVAC technician may be servicingone HVAC system 120 in the cluster 110, e.g. As part of the servicing,the technician may change one or more parameters that in turn changes anaspect of the performance of the system 120 being serviced. It may bedesired to similarly modify all the systems 120 in the cluster 110 soall the systems 120 operate with essentially the same characteristics.

As mentioned previously, the technician is very unlikely to have aportable computer available to assist configuring the other systems 120in the cluster. Thus, in conventional practice the technician typicallyrepeats the configuration process for each other system 120 in thecluster. In cases in which an HVAC system includes an interface similarto the control unit 270, but lacks the PFMD port 340, the technician mayneed to enter multiple parameter changes via a keypad, involvinghundreds of key presses. When an HVAC cluster includes more than a smallnumber of HVAC systems, the time required to enter changes to all thesystems is time consuming and may result in considerable expense.

In contrast to conventional practice, in a step 520 the techniciantransfers the configuration file from the PFMD 480, previously obtainedfrom the first system 120, to a second HVAC system 120. Themicrocontroller 410 is configured to transfer the configuration filedirectly, e.g., without the assistance of another computer system, fromthe PFMD 480 to the parameter memory 430 of the second HVAC system 120.If the configuration file is encrypted, as discussed below, themicrocontroller 410 may also decrypt the contents thereof before storingthe parameters in the parameter memory 430. The control unit 270 may beconfigured to effect the transfer with a small number of key strokes,resulting in rapid reconfiguration of the second system 120. Of course,the second system 120 need not be in close proximity to the first system120. The technician may store the PFMD 480 in his or her pocket andreconfigure any number of other systems 120 over any time period at anylocation. The technician may even have several PFMDs 480, one each fordifferent models or configurations of the HVAC system 120. In someembodiments the microcontroller 410 stores the configuration file with atime stamp or other identifying string that allows the technician toretrieve one of two or more configuration files from the PFMD 480 thatcorresponds to a desired configuration of the system 120. Thus multiplesystem configurations may be stored on and retrieved from a single PFMD480.

Finally, in a step 530 the first and the second HVAC systems 120 areoperated in conformity with the configuration file stored in theparameter memory 430.

In various embodiments the control unit 270 is configured to generate aservice verification report. The service verification report is a datastructure that may be written to the PFMD 480. In various embodimentsthe data structure includes various data relevant to determining thatthe service technician performed services to the system 120. Examples ofsuch data include, without limitation, a date, a time, a serial numberof an HVAC unit, a technician ID, configuration parameters as configuredprior to the service, and configuration parameters as configured afterthe service. The system control unit 270 is configured in variousembodiments to copy the service verification report from a memory, e.g.,the parameter memory 430, to the PFMD 480. The transfer may be initiatedby key strokes by the technician via the keypad 320, e.g. In someembodiments the service verification report is generated “on the fly”when a request to transfer the report to the PFMD 480 is made. In suchcases, the microcontroller may draw from data available in otherlocations or contexts in the system 120, e.g., the configuration file,time and data from a system clock, etc., while generating the servicereport. The service verification report may be provided to the HVACoperator to verify the presence of the technician at the system 120being serviced, as described further below.

Turning to FIG. 6, illustrated is an embodiment of a portion of aservice verification report 600. The report 600 may have as many datafields as are desired. The report 600 includes a number of fields forillustration. A field 605 may include an identifying string, such as afile name. A field 610 may include a time stamp, date stamp or similarmanner of indicating a time the report 600 is generated. A field 615 mayindicate a control mode in which the system 120 is configured tooperate, such as, e.g., heating or cooling. A field 620 may includeoperating set points, such as a target cooling temperature or a targetheating temperature. A field 625 may include backup set points, e.g.,set points that are used if a primary control fails. A field 630 mayinclude a parameter indicating whether the system is configured to usefresh or tempered air. A field 635 may include a parameter indicatingwhether discharge air is heated or cooled. A field 640 may include aparameter indicating whether the system 120 is configured for multistageair flow. A field 645 may include a unit serial number. Fields 641, 642and 643 may respectively include equipment operational information suchas runtime hours for major parts, error codes for equipment failures,and reports from self or installation tests. And a field 650 may includean end-of-file marker.

A feature of various embodiments presented herein is the ability toensure integrity of data on the PFMD 480. A service provider might betempted to tamper with data on the PFMD 480, such as a configurationfile or a service verification report, to create the false appearancethat service was performed. It is an objective of various embodimentsherein to provide a high confidence level on the part of an HVACoperator that data provided via the PFMD 480 to support a service claimis authentic.

Thus, in some embodiments the report 600 includes authentication data655. The authentication data 655 may be used to verify the integrity ofthe report 600 when the HVAC operator determines if a service claimproperly reflects services rendered. The authentication data 655 mayinclude, e.g., values derived from other data fields in the report 600.For example, the authentication data 655 may include a CRC computed fora proper subset of the data fields. The authentication data 655 may beplaced in multiple locations in the report 600, and may be encrypted. Insome cases, multiple inclusions of identical information may be placedin multiple locations in the report 600, with different encryptionschemes used for duplicate inclusions. In some cases, the entire serviceverification report is encrypted by the microcontroller 410 when writtento the PFMD 480.

More generally, a service verification report, such as the report 600,is but one type of electronic verification file that may be used toverify the presence of the service provider at the system 120. Thesystem profile may also be used in this manner, as well as anyelectronic verification file that includes data that may obtained easilyby the operator only by being present at the system 120.

After the electronic verification file is transferred to the PFMD 480,the service provider may transport the PFMD 380 to a location from whichhe or she may provide the electronic verification file to the HVACoperator in a form the HVAC operator may use to verify the presence ofthe service provider at the system 120. For example, the serviceprovider may provide the PFMD 380 to the HVAC operator, may upload theelectronic verification file to a database or server accessible to theHVAC operator, or may attach the electronic verification file to anelectronic message (e.g., email). An electronic message may, forexample, include a service invoice and the service verification file.The HVAC operator may then authenticate the service verification file,verify requested services were actually performed, and remit payment tothe service provider.

A method generally designated 700 of verifying the performance ofservice using an electronic verification file is presented in FIG. 7.The method is described without limitation with reference to the serviceverification report 600, and the system 120 and components thereof. In astep 710, a service provider causes the system 120 to transfer theelectronic verification file to the PFMD 480. As described earlier, theservice provider may cause the transfer by selecting appropriatecommands on the system control unit 270. In a step 720, the serviceprovider, or an agent thereof, provides the electronic verification fileto the HVAC operator. The HVAC operator may process the electronicverification file by, e.g., decrypting the file, computing and verifyinga CRC value, comparing serial numbers or model numbers with an equipmentdatabase, comparing a service provider serial number with a serviceprovider database, etc. The HVAC operator may also receive an invoiceassociated with the services rendered by the service provider, eitherwith the electronic verification file or by a separate route. In a step730 the HVAC operator remits payment or credits an account of theservice provider in response to verifying the authenticity of thereceived electronic verification file, and in some cases verifying thatparameters contained by the system verification file indicate serviceswere actually performed.

The control unit 270 is also configured in various embodiments toprovide additional useful functionality via the PFMD port 340. In oneembodiment, the control unit 270 is configured to update the programinstructions located on the program memory 420 with updated programinstructions located on the PFMD 480. The update may be in response tocommands entered via the keypad 320, or automatically when themicrocontroller 410 recognizes updated firmware on the PFMD 480.

In an embodiment the control unit 270 is configured to store controllerstatus logs and error logs on the PFMD 480. These data may be used,e.g., for later analysis by the HVAC operator, manufacturer or dealer.Such data may be uploaded to a service database, or otherwisetransmitted to an interested party. In some cases system 120 operationaldata are transferred to the PFMD 480 and transferred to a remote serviceprovider, such as a central manufacturer service center, or “help desk.”A remote agent, either human or machine, may use the operational data todiagnose system errors, malfunctions, etc. Possession of these data bythe remote agent is expected to simplify diagnosis by the remote agentand reduce the time and expense needed to obtain advice, a diagnosis ofan error, or other information from the remote agent. In some cases, thedata are transferred to an analyst to determine operational trends ofthe system 120. For example, operational parameters may reveal trendsrelevant to preventative maintenance or reduction of energy consumption.

The control unit 270 may also be configured to support various utilityfunctions via the PFMD port 340. For example, when configured as a USBport, the PFMD port may provide power to a light or a fan, or may chargea portable electronic device such as a cell phone.

The control unit 270 may also be configured to provide some diagnosticcapability via the PFMD port 340. For example, the control unit 270 mayprovide system data such as serial numbers, configuration data, firmwarerevisions, coolant pressure and error codes to a computer coupled to thePFMD port 380. In some embodiments, the control unit 270 is configuredto distribute power to it through the PFMD port 340 to energize sensorsor other electronics necessary to effect the transfer of theaforementioned data. Such embodiments may have particular utility in amanufacturing or shipping context, to provide a means to determine theidentity or basic health of the system 120 without the need to removepacking materials, open panels, etc.

Turning now to FIG. 8A, a method generally designated 800 ofmanufacturing an HVAC system is presented. The method is describedwithout limitation with reference to the system 120 and componentsthereof. In a step 810, a housing such as the enclosure 205 isconfigured to contain components of the HVAC system 120. In a step 820,an HVAC system control unit such as the control unit 270, is locatedwithin the housing. The interface includes a microcontroller forcontrolling an operation of the HVAC system. In a step 830 a memory isincluded within the HVAC system control unit and associated with themicrocontroller. In a step 840 the memory is configured to store dataassociated with operation of the HVAC system. In a step 850, the HVACsystem control unit is provided with a portable flash memory deviceinterface for coupling the PFMD directly to the microcontroller.

FIG. 8B presents additional optional steps in the method 800. In a step860, the HVAC system control unit is configured to download a firmwareupdate from the portable memory device. The firmware update may beinstalled by the microcontroller 410 in the program memory 420, e.g. Ina step 870 the HVAC system control unit is configured to download apreviously stored configuration file from the portable flash memorydevice. In a step 880, the HVAC system control unit is configured toadapt the HVAC system to operate in conformity with the previouslystored configuration file. In a step 890, the HVAC system control unitis configured to store the data on the PFMD in an encrypted form.

Those skilled in the art to which this application relates willappreciate that other and further additions, deletions, substitutionsand modifications may be made to the described embodiments.

1. An HVAC system, comprising: an enclosure for containing components ofsaid HVAC system; an HVAC system control unit including amicrocontroller located within said enclosure for controlling anoperation of said HVAC system; said HVAC system control unit furtherincluding a memory associated with said microcontroller and configuredto store data associated with operation of said HVAC system, saidmicrocontroller configurable to directly transfer said data between saidmemory and a portable flash memory device; and said HVAC system controlunit further including a portable flash memory device interface forcoupling said portable flash memory device directly thereto.
 2. The HVACsystem as recited in claim 1, wherein said data comprises a systemprofile.
 3. The HVAC system as recited in claim 1, wherein said datacomprises a service verification report.
 4. The HVAC system as recitedin claim 1, wherein said interface is further configured to download afirmware update from said portable memory device.
 5. The HVAC system asrecited in claim 1, wherein said portable flash memory device is a USBflash drive.
 6. The HVAC system as recited in claim 1, wherein saidinterface is further configured to download from said portable flashmemory device a previously stored configuration file, and to configuresaid HVAC system to conform to said previously stored configurationfile.
 7. The HVAC system as recited in claim 1, wherein saidmicrocontroller is configurable to store said data on said portableflash memory device in an encrypted form.
 8. A method of manufacturingan HVAC system, comprising: configuring an enclosure to containcomponents of an HVAC system; locating within said enclosure an HVACsystem control unit including a microcontroller for controlling anoperation of said HVAC system; including within said HVAC system controlunit a parameter memory associated with said microcontroller andconfiguring said parameter memory to store data associated withoperation of said HVAC system, said microcontroller configurable todirectly transfer said data between said memory and a portable flashmemory device; and providing said HVAC system control unit with aportable flash memory device interface for coupling said portable flashmemory device directly to the microcontroller.
 9. The method as recitedin claim 8, wherein said data comprises a system profile.
 10. The methodas recited in claim 8, wherein said data comprises a serviceverification report.
 11. The method as recited in claim 8, furthercomprising configuring said HVAC system control unit to download afirmware update from said portable flash memory device.
 12. The methodas recited in claim 8, wherein said portable flash memory device is aUSB flash drive.
 13. The method as recited in claim 8, furthercomprising configuring said HVAC system control unit to: download fromsaid portable flash memory device a previously stored configurationfile; and adapt said HVAC system to operate in conformity with saidpreviously stored configuration file.
 14. The method as recited in claim8, further comprising configuring said HVAC system control unit to storesaid data on said portable flash memory device in an encrypted form. 15.An HVAC system control unit, comprising: a microcontroller forcontrolling an operation of an HVAC system; a memory associated withsaid microcontroller and configured to store data associated withoperation of said HVAC system, said microcontroller configurable todirectly transfer said data between said memory and a portable flashmemory device; and a portable flash memory device interface for couplingsaid portable flash memory device directly to said microcontroller. 16.The HVAC system control unit as recited in claim 15, wherein said datacomprises a system profile.
 17. The HVAC system control unit as recitedin claim 1, wherein said data comprises a service verification report.18. The HVAC system control unit as recited in claim 15, wherein saidinterface is further configured to download a firmware update from saidportable memory device.
 19. The HVAC system control unit as recited inclaim 15, wherein said portable flash memory device is a USB flashdrive.
 20. The HVAC system control unit as recited in claim 15, whereinsaid interface is further configured to download from said portableflash memory device a previously stored configuration file, and toconfigure said HVAC system to conform to said previously storedconfiguration file.
 21. The HVAC system control unit as recited in claim15, wherein said microcontroller is configurable to store said data onsaid portable flash memory device in an encrypted form.